-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New docn features and update to documentation #213
Conversation
docn/CMakeLists.txt
Outdated
@@ -1,9 +1,11 @@ | |||
project(docn Fortran) | |||
set(SRCFILES ocn_comp_nuopc.F90 | |||
docn_datamode_copyall_mod.F90 | |||
docn_datamode_copyall_mod.F90 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
align these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything is now re-aligned under SRCFILES.
@@ -44,7 +45,7 @@ | |||
|
|||
<entry id="DOCN_MODE"> | |||
<type>char</type> | |||
<valid_values>prescribed,sst_aquap1,sst_aquap2,sst_aquap3,sst_aquap4,sst_aquap5,sst_aquap6,sst_aquap7,sst_aquap8,sst_aquap9,sst_aquap10,sst_aquapfile,som,som_aquap,sst_aquap_constant,interannual,null</valid_values> | |||
<valid_values>prescribed,sst_aquap1,sst_aquap2,sst_aquap3,sst_aquap4,sst_aquap5,sst_aquap6,sst_aquap7,sst_aquap8,sst_aquap9,sst_aquap10,sst_aquapfile,som,som_aquap,sst_aquap_constant,interannual,cplhist</valid_values> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is null no longer a valid option?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You never needed null - and it made no sense to have it there. So it is no longer a valid option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to run this with the additional fields Foxx_taux
and Foxx_tauy
being written out, but got an error. I'm testing now with the original variable list -- is it reasonable to expect docn to be able to write out the two components of tau, or would that come from a different component? I think MOM and POP can both receive the above field, though it's entirely possible I mistyped the variable names in my xmlchange
command.
My sandbox was incomplete -- I forgot to update CMEPS to the branch in ESCOMP/CMEPS#341 so I'm rebuilding and testing again. Sorry, the caffeine hasn't kicked in yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I updated my sandbox correctly, I was able to run (and write the additional tau fields in the history files). I really like the introduction of DOCN_IMPORT_FIELDS
, it makes it really easy to modify what fields we want output!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this also requires update in the documentation. If you don't mind could you include information about these new docn modes to the Section 5 (https://escomp.github.io/CDEPS/versions/master/html/docn.html). I think we don't need to test UFS for this PR since it does not touching exiting ones. Do you agree with me? If you want I could test it.
@uturuncoglu - I agree about not having to test with the UFS. How do I update the web pages for the documentation. Once the PR is merged - does it automatically update the web pages? Can we please chat today? |
…l cdeps variables
@uturuncoglu @jedwards4b - I have updated the CDEPS documentation quite a bit. I have added new documentation for this PR as well as documenting the env_run.xml variables for each data component that appear in env_run.xml. |
@mvertens once the doc sources ready. we need to compile it and push to gh-pages with another PR. Then you could see the update in the pages. |
THis may be a good opportunity to add the stuff that Ufuk recently wrote up as well. |
@jedwards4b agree. once this PR in. Maybe I could push those as a part of this PR. What do you think? Of course after ESMF meeting today. |
@uturuncoglu - how do you do a PR to gh-pages? |
When you open the PR - you direct it to the gh-pages branch of the repo instead of main. |
@jedwards4b- in looking at the gh-pages branch it looks like this is just the output from running make html in the doc directory. This seems really awkward if this is indeed what we are doing. Do you agree? |
@mvertens you need to checkout gh-pages branch. Create your branch from it such as updatedoc. Then, copy your compiled doc (the directory that has doctrees and html) under master directory. Then commit your changes. then you could create PR to gh-pages. |
@uturuncoglu - thanks. |
@mvertens @jedwards4b i am planing to add NUOPC cap documentation that I wrote for the UFS technical documentation. As a part of this, I need to compile the documentation and also need to create PR for CDEPS gh-pages. So, this will also include documentation that is added as a part of this PR. @mvertens do you want me to go and do that. So, there is no to have two PR to gh-pages (one for doc that is a part of this PR and other for NUOPC cap doc.) |
Description of changes
New docn features
Specific notes
This PR adds two new features to docn:
For now the user will have to set the following variables in user_nl_docn_streams:
The new xml variable is DOCN_IMPORT_FIELDS
If
DOCN_IMPORT_FIELDS=none,
then no ocean import fields will be advertised by the ocean and therefore written out in the mediator history fileIf
DOCN_IMPORT_FIELDS= Faxa_bcph:Faxa_dstdry:Faxa_dstwet:So_duu10n:Si_ifrac
then these fields will be written out to the mediator history file.Contributors other than yourself, if any: @jedwards4b @mnlevy1981
CDEPS Issues Fixed (include github issue): None
Are there dependencies on other component PRs (if so list): Yes. This PR needs to be accompanied by an associated CMEPS PR (TBD) and resolves the CMEPS issue ESCOMP/CMEPS#340
Are changes expected to change answers (bfb, different to roundoff, more substantial): bfb
Any User Interface Changes (namelist or namelist defaults changes): Yes -see new xml variable above
Testing performed (e.g. aux_cdeps, CESM prealpha, etc):
Hashes used for testing: cesm2_3_beta11